Mechanism for realizing LWA/LWIP aggregator function

ABSTRACT

In one implementation, the method comprises, in response to obtaining a request to associate an electronic device with the one or more WLAN termination nodes: generating, between a base station and a networking device, a control link based on a first identifier associated with the base station; generating, between the networking device and a first WLAN termination node, a control link based on a second identifier that corresponds to a pseudonym for the base station; and associating the first and second identifiers in a control table. The method further comprises: instantiating, between the base station and the networking device, a first data tunnel associated with a first tunneling protocol; instantiating, between the networking device and the first WLAN termination node, a second data tunnel associated with a second tunneling protocol; and associating the first and second data tunnels.

TECHNICAL FIELD

The present disclosure relates generally to networking, and inparticular, to link generating and tunnel instantiating in aheterogeneous network.

BACKGROUND

Certain networking deployments allow an electronic device to communicatewith multiple networks associated with different radio accesstechnologies (RATs). The multiple networks are sometimes collectivelyreferred to as a heterogeneous network. A heterogeneous network providesa number of advantages, such as increased coverage, reliability, andspectrum efficiency. Certain heterogeneous networks facilitateconcurrent communications between the electronic device and the networksassociated with different RATs.

However, current deployments of these networks have numerousshortcomings. These deployments utilize inefficient link generation andtraffic mapping schemes between nodes associated with differentnetworks. For example, current deployments specify a separate linkbetween each networking node associated with a first RAT and eachnetworking node associated with a second RAT. These require largeresource utilizations at the various networking nodes. As anotherexample, networking nodes associated with a particular RAT receive datapackets according to a non-native protocol. Consequently, thesenetworking nodes must expend great computational resources for mappingpurposes.

BRIEF DESCRIPTIONS OF THE DRAWINGS

For a better understanding of aspects of the various implementationsdescribed herein and to show more clearly how they may be carried intoeffect, reference is made, by way of example only, to the accompanyingdrawings.

FIG. 1 illustrates a simplified diagram of a network environmentaccording to various implementations.

FIG. 2 illustrates a conceptual diagram of a networking environmentaccording to various implementations.

FIG. 3 illustrates a conceptual diagram of a networking device accordingto various implementations.

FIG. 4 illustrates exemplary data structure diagrams for a control flowmapping table and a data flow mapping table according to variousimplementations.

FIG. 5 illustrates a conceptual diagram of a setup flow associated witha networking device according to various implementations.

FIG. 6 illustrates a flowchart representation of a method of linkgenerating and tunnel instantiating according to variousimplementations.

FIGS. 7A-7C illustrate a flowchart representation of a method of linkgenerating and tunnel instantiating according to variousimplementations.

FIG. 8 illustrates a block diagram of an example of a networking devicein accordance with various implementations.

In accordance with common practice the various features illustrated inthe drawings may not be drawn to scale. Accordingly, the dimensions ofthe various features may be arbitrarily expanded or reduced for clarity.In addition, some of the drawings may not depict all of the componentsof a given system, method or device. Finally, like reference numeralsmay be used to denote like features throughout the specification andfigures.

DESCRIPTION OF EXAMPLE EMBODIMENTS

Numerous details are described herein in order to provide a thoroughunderstanding of illustrative implementations shown in the drawings.However, the drawings merely show some example aspects of the presentdisclosure and are therefore not to be considered limiting. Those ofordinary skill in the art will appreciate from the present disclosurethat other effective aspects and/or variants do not include all of thespecific details described herein. Moreover, well-known systems,methods, components, devices and circuits have not been described inexhaustive detail so as not to unnecessarily obscure more pertinentaspects of the implementations described herein.

Overview

Various implementations disclosed herein include methods, networkingdevices, and apparatuses for link generating and tunnel instantiatingbetween networking nodes associated with different radio accesstechnologies (RATs). The method comprises, at a networking devicecommunicatively coupled to a base station and one or more wireless localarea network (WLAN) termination nodes: obtaining a request to associateone or more electronic devices with the one or more WLAN terminationnodes, wherein the one or more electronic devices are associated withthe base station. The method further comprises in response to obtainingthe request to associate the one or more electronic devices with the oneor more WLAN termination nodes: generating, between the base station andthe networking device, a control link based at least in part on a firstidentifier included in the request, wherein the first identifier isassociated with the base station; generating, between the networkingdevice and the first WLAN termination node among the one or more WLANtermination nodes, a control link based at least in part on a secondidentifier associated with the base station, wherein the secondidentifier corresponds to a pseudonym for the base station; andassociating the first identifier with the second identifier in a controlflow mapping table. The method further comprises instantiating, betweenthe base station and the networking device, a first data tunnelassociated with a first tunneling protocol. The method further comprisesinstantiating, between the networking device and the first WLANtermination node among the one or more WLAN termination nodes, a seconddata tunnel associated with a second tunneling protocol different fromthe first tunneling protocol. The method further comprises associatingthe first data tunnel with the second data tunnel in a data flow mappingtable.

In accordance with various implementations, a networking device includesone or more processors, a non-transitory memory, and one or moreprograms. The one or more programs are stored in the non-transitorymemory and configured to be executed by the one or more processors andthe one or more programs include instructions for performing or causingperformance of any of the methods described herein. In accordance withsome implementations, a non-transitory computer readable storage mediumhas stored therein instructions, which, when executed by one or moreprocessors of a networking device, cause the networking device toperform or cause performance of any of the methods described herein. Inaccordance with some implementations, a networking device includes: oneor more processors, a non-transitory memory, and means for performing orcausing performance of any of the methods described herein.

Example Implementations

Certain current deployments facilitate communication between multiplenetworks associated with different radio access technologies (RATs) andone or more electronic devices. These networks are sometimescollectively referred to as a heterogeneous network. Certain currentdeployments allow one or more electronic devices to concurrentlycommunicate with the networks.

However, current deployments inefficiently facilitate thiscommunication. For example, in certain heterogeneous networks includinga cellular network and a wireless local area network (WLAN), there mustbe a separate link between each base station and each wirelesstermination node. In order words, there are an M×N number of links,where M is the number of base stations and N is the number of wirelesstermination nodes. Generating this large number of links is complex andtherefore computationally expensive. Moreover, storage resources aredrained because, for example, each wireless termination node must storeconfiguration data for numerous base stations in order to facilitatelink generation.

Another problem with current deployments is that because these networksare associated with different RATs, data packets are received at aparticular node according to a protocol that is not native to theparticular node. For example, in certain deployments involvingconcurrent LTE and WLAN communications, the base station (e.g., eNodeB)receives data packets from a wireless termination node according to theWLAN-based generic routing encapsulation (GRE) tunnel protocol.Continuing with the example, the wireless termination node converselyreceives data packets from the base station according to thecellular-based GPRS tunneling protocol user plane (GTP-U). This raisesissues because each node is pre-configured to receive data packetsaccording to its native respective protocol.

Accordingly, the present disclosure is directed to methods, devices, andapparatuses for link generating and tunnel instantiating in aheterogeneous network having networks associated with different RATs. Invarious implementations, this involves an electronic device inconcurrent communications with a cellular network and a WLAN.

FIG. 1 illustrates a simplified diagram of a network environment 100according to various implementations. The networking environment 100includes an electronic device 101 in communication with a cellularnetwork 102 and a WLAN 103. In various implementations, the electronicdevice 101 concurrently communicates with the cellular network 102 andthe WLAN 103. It is to be appreciated that the term concurrent as usedin the present disclosure includes substantially concurrent.

The electronic device 101 can be any device that includes multipleradios so as to allow it to communicate with multiple RATs, such ascellular and IEEE 802.11xx-based technologies (e.g., Wi-Fi). Forexample, the electronic device 101 corresponds to user equipment (UE)such as a mobile phone, laptop, tablet, set-top box, over-the-top box,video game console, or the like. In another example, the electronicdevice 101 corresponds to an Internet of Things (IoT) sensor, anautonomous driving vehicle system, a remote-controlled drone, avirtual/augmented reality system, or the like.

A base station 104 provides the electronic device 101 with connectivityto the cellular network 102 associated with a cellular RAT. Examples ofcellular RATs include technologies defined by the 3rd GenerationPartnership Project (3GPP), such as 3G, 4G, LTE, 5G, and the like. Invarious implementations, the base station 104 corresponds to a cellularbase station. For example, in some implementations, the base stations104 corresponds to an eNodeB (e.g., in 4G and LTE) and/or a gNodeB(e.g., in 5G). In various implementations, the base station 104corresponds to a picocell. In various implementations, the base station104 corresponds to a home eNodeB (HeNodeB), such as a Femtocell Gateway(F-GW)).

Although not depicted, in various implementations, the networkenvironment 100 includes two or more base stations 104. In someimplementations, the two or more base stations 104 provide overlappingcoverage areas for the electronic device 101. In other words, theelectronic device 101 is positioned so as to be connectable to two ormore of the one or more base stations 104 at the same time. In someimplementations, the electronic device 101 is considered within thecoverage area of a respective base station among the one or more basestations 104 when there is an adequate signal strength between theelectronic device 101 and the respective base station, as can indicatedby, for example, a received signal strength indicator (RSSI).

An access point 105 provides the electronic device 101 with connectivityvia an Ethernet link to the WLAN 103 associated with a wireless RAT.Examples of wireless RATs include IEEE 802.11xx-based networks, such asWi-Fi and WiMax.

Although not depicted, in various implementations, the networkenvironment 100 includes two or more access points 105 that provideoverlapping coverage areas for the electronic device 101. In otherwords, the electronic device 101 is positioned so as to be connectableto multiple access points 105 at the same time. In some implementations,the electronic device 101 is considered within the coverage area of theaccess point 105 when there is an adequate signal strength between them,as can indicated by, for example, a received signal strength indicator(RSSI). For example, if the electronic device 101 is located in ashopping mall, there may be access points associated with stores closeto each other that off Wi-Fi (e.g., two coffee shops near each other)but the electronic device 101 is connected to the access point to whichit has a higher RSSI.

The WLAN 103 includes a wireless termination node 106. Although notdepicted, in various implementations, the WLAN 103 includes two or morewireless termination nodes 106. In various implementations, the wirelesstermination node 106 provides connectivity between a networking device107 and the access point 105. In various implementations, where theelectronic device 101 is within the coverage area of multiple accesspoints 105, there are multiple wireless termination nodes 106. In someimplementations, there are an equal number of wireless termination nodes106 as access points 105. In some implementations, there are fewerwireless termination nodes 106 than access points 105. For example, insome implementations, a wireless termination node 106 is integrated with(e.g., co-located or combined with) an access controller (AC) (notshown), and the AC manages multiple access points 105. In someimplementations, the wireless termination node 106 and the AC areseparate (e.g., not integrated).

The networking device 107 provides connectivity between the wirelesstermination node 106 and the base station 104. As is further describedin the present disclosure, the networking device 107 implements linkgeneration and mapping between the cellular network 102 and the WLAN 103according to various implementations. The networking device 107 includesa processor, a non-transitory memory, one or more input interfaces, andone or more output interfaces. In some implementations, the networkingdevice 107 comprises its own node. In some implementations, thenetworking device 107 is integrated with (e.g., co-located or combinedwith) another node. For example, in some implementations, the networkingdevice 107 is integrated with an X2 gateway node, which facilitates dataplane and control plane signaling between two or more base stations 104(e.g., macrocells, home eNodeBs (HeNBs), picocells, or the like). Insome implementations, when the networking device 107 is integrated with(e.g., co-located or combined with) an existing node of a deployment,the deployment need not be changed (e.g., nodes need not be added to theexisting deployment).

In various implementations, the electronic device 101 is concurrentlyconnected to multiple networks associated with different RATs (e.g., thecellular network 102 and the WLAN 103). Concurrent connectivity canoccur according to various technologies. One such technology is LTE-WLANaggregation (LWA). LWA allows the electronic device 101 to concurrentlyutilize its LTE link and WLAN link. Under LWA, the infrastructure of theWLAN 103 communicates with the base station 104 (e.g., eNodeB), but notwith the core cellular network. This eliminates the need forWLAN-specific core network nodes, as is specified by previous deploymenttypes, such as LTE/WLAN interworking via untrusted WLAN accessdeployments (e.g., S2B). The wireless termination node 106 in LWA is alogical node referred to as a WLAN termination (WT). In someimplementations, the networking device 107 is integrated with the WT. Insome implementations, the base station 104 and the WT communicate withthe networking device 107 via a standardized interface referred to asXw, as is defined in 3GPP technical specifications (TSs) 36.463-36.465.In some implementations, the control links between the base station 104and the networking device 107, and between the WT and the networkingdevice 107, are referred to as Xw links.

Another technology that can be utilized for concurrent communications isLTE-WLAN Radio Level Integration with IPsec Tunnel (LWIP). Under LWIP,an IPsec tunnel provides connectivity between the electronic device 101and the WLAN 103. The IPsec tunnel is transparent to infrastructure ofthe WLAN 103 and therefore, unlike LWA, there are no standardizedinterfaces. The wireless termination node 106 in LWIP is referred to asan IP-SecGW (IP security gateway). In some implementations, thenetworking device 107 is integrated with the IP-SecGW.

FIG. 2 illustrates a conceptual diagram of a network environment 200according to various implementations. The networking device 107 providesconnectivity between wireless termination nodes 106 a-106 n and basestations 104 a-104 n.

The network environment 200 includes an M+N number of control links,where M is the number of base stations 104 a-104 n and N is the numberof wireless termination nodes 106 a-106 n connected to the networkingdevice 107. This is fewer than the M×N number of control links presentin current systems, resulting in resource savings. These control linksare effectively aggregated by the networking device 107.

Additionally, the networking device 107 provides improved data planeperformance by mapping the cellular data packet protocol to the WLANdata packet protocol, and vice versa. This mapping improves networkperformance by providing the wireless termination nodes 106 a-106 n andthe base stations 104 a-104 n with data packets according to theirrespective tunneling protocols. Additionally, the mapping leads tocomputational savings because the base stations 104 a-104 n need not beinvolved in control plane signalling. Moreover, the mapping reduces theamount of stored configuration information at the wireless terminationnodes 106 a-106 n because they need not be aware of certain propertiesof the base stations 104 a-104 n.

FIG. 3 illustrates a conceptual diagram of the networking device 107according to various implementations. According to variousimplementations, the networking device 107 functions to generate controllinks between wireless termination nodes and base stations and to mapthe flow of data between them.

In some implementations, as shown in FIG. 3, the networking device 107includes a link generator 301. The link generator 301 generates controlbetween base stations and wireless termination nodes (e.g., the basestations 104 a-104 n and the wireless termination nodes 106 a-106 n inFIG. 2). In some implementations, the link generator 301 generates thecontrol links according to known control plane protocols. For example,in some implementation, the link generator 301 generates an Xw link byusing an Xw addition request message and an Xw addition requestacknowledgement message. After a control link is generated between thenetworking device 107 and a particular base station, the networkingdevice 107 appears to be a wireless termination node from theperspective of the particular base station. After a control link isgenerated between the networking device 107 and a particular wirelesstermination node, the networking device 107 appears to be a base stationfrom the perspective of the particular wireless termination node.

In various implementations, the link generator 301 populates a controlflow mapping table 302 in conjunction with generating the control links.The control flow mapping table 302 can be part of any type of memoryresource at the networking device 107. The control flow mapping table302 includes a mapping between identification information identifyingthe base stations and identification information identifying thewireless termination nodes. An exemplary control flow mapping table 302is illustrated in FIG. 4. In various implementations, the link generator301 obtains identification information from a base station and storesthe identification information in the control flow mapping table 302. Invarious implementations, the link generator 301 generates identificationinformation identifying a wireless termination node and stores theidentification information in the control flow mapping table 302. Insome implementations, the link generator 301 generates identificationinformation identifying a wireless termination node based onidentification information identifying one or more base stations.

In some implementations, as shown in FIG. 3, the networking device 107includes a control flow mapper 303. The control flow mapper 303 utilizesthe control flow mapping table 302 in order to map control packetsbetween base stations and wireless termination nodes. The control flowmapper 303 modifies a control packet received from a particular basestation so that the control packet reaches the appropriate destinationwireless termination node, and vice verse. In various implementations,the control flow mapper 303 modifies the value of identificationinformation included in an incoming control packet. The identificationinformation is changed to a value associated with the appropriatelymapped destination node.

In some implementations, as shown in FIG. 3, the networking device 107includes a tunnel instantiator 304. The tunnel instantiator 304instantiates data tunnels associated with a first protocol between thenetworking device 107 and corresponding base stations. The tunnelinstantiator 304 also instantiates data tunnels associated with a secondprotocol between the networking device 107 and corresponding wirelesstermination nodes. The instantiated data tunnels carry data packetsbetween base stations and wireless termination nodes via the networkingdevice 107.

In various implementations, the tunnel instantiator 304 populates a dataflow mapping table 305 in conjunction with instantiating data tunnels.The data flow mapping table 305 can be part of any type of memoryresource at the networking device 107. An exemplary data flow mappingtable 305 is illustrated in FIG. 4. The data flow mapping table 305includes identifiers identifying the instantiated data tunnels. The dataflow mapping table 305 includes mappings between identifiers identifyingdata tunnels associated with base stations and identifiers identifyingdata tunnels associated with wireless termination nodes.

In some implementations, as shown in FIG. 3, the networking device 107includes a data flow mapper 306. The data flow mapper 306 utilizes thedata flow mapping table 305 in order to map data packets between basestations and wireless termination nodes. The data flow mapper 306 maps adata packet received from a base station according to a first protocolto a data packet destined for a wireless termination node according to asecond protocol. The data flow mapper 306 also maps a data packetreceived from a wireless termination node according to the secondprotocol to a data packet destined for a base station according to thefirst protocol. This effectively provides the receiving networking nodewith data packets in their native format, leading to improvedtransmission performance. As an example, an incoming data packetreceived at the networking device 107 includes an identifier indicatingthe data tunnel through which it was received. Continuing with thisexample, the data flow mapper 306, based on entries of data flow mappingtable 305, modifies the identifier of the received data packet tocorrespond to the data tunnel through which it is to be forwarded.

In various implementations the first protocol corresponds to a generalpacket radio service (GPRS) tunneling protocol user plane (GTP-U). Invarious implementations, the second protocol corresponds to a genericrouting encapsulation (GRE) protocol.

According to some implementations, data packets transported between thebase station(s) and the wireless termination node(s) correspond toInternet Protocol (IP) data packets (e.g., IPv4 and/or IPv6). Accordingto some implementations, the data packets correspond to point-to-point(PPP) data packets. According to some implementations, the data packetscorrespond to a combination of IP data packets and PPP data packets.According to some implementations, data packets sent from and/orreceived at the wireless termination node are encapsulated, such as anIP data packet (e.g., IP payload) encapsulated by the GRE protocol.

FIG. 4 illustrates exemplary data structure diagrams for a control flowmapping table 302 and a data flow mapping table 305 according to variousimplementations. In various implementations, the control flow mappingtable 302 is populated by a link generator (e.g., the link generator 301in FIG. 3) and utilized by a control flow mapper (e.g., the control flowmapper 303 in FIG. 3). In various implementations, the data flow mappingtable 305 is populated by a tunnel instantiator (e.g., the tunnelinstantiator 304 in FIG. 3) and utilized by a data flow mapper (e.g.,the data flow mapper 306 in FIG. 3).

The tables 302 and 305 of FIG. 4 assume a networking environment withfour electronic devices (electronic device #1-electronic device #4), twobase stations (BS #1 and BS #2), and four wireless termination nodes,each of which providing coverage to one of the four electronic devices.In other words, each electronic device is being serviced by one wirelesstermination node. However, one or ordinary skill in the art willappreciate that the control flow mapping table 302 and the data flowmapping table 305 can account for various situations in which one ormore electronic devices are each being concurrently serviced by numerouswireless termination nodes. Moreover, one of ordinary skill in the artwill appreciate that the control flow mapping table 302 and the dataflow mapping table 305 can account for more or fewer of either or bothof the base stations and/or wireless termination nodes. Moreover, invarious implementations, one of ordinary skill in the art willappreciate that the control flow mapping table 302 may be structuredand/or formatted differently.

The control flow mapping table 302 includes base station identifiers inorder to identify a particular base station with a particular electronicdevice. The control flow mapping table 302 includes identifier values of1001 and 1002 for identifying BS #1 with electronic device #1 andelectronic device #2, respectively. The control flow mapping table 302includes identifier values of 2001 and 2002 for identifying BS #2 withelectronic device #3 and electronic device #4, respectively.

The control flow mapping table 302 provides a mapping between the twobase stations identifiers and identifiers associated with the fourwireless termination nodes. The control flow mapping table 302 providespseudonym identifiers for the four wireless termination nodes based onthe base station identifiers. With respect to electronic device #1, thecontrol flow mapping table 302 maps the identifier value of 1001 to apseudonym identifier value of 3001 associated with the first wirelesstermination node. With respect to electronic device #2, the control flowmapping table 302 maps the identifier value of 1002 to a pseudonymidentifier value of 3005 associated with the second wireless terminationnode. With respect to electronic device #3, the control flow mappingtable 302 maps the identifier value of 2001 to a pseudonym identifiervalue of 5001 associated with the third wireless termination node. Withrespect to electronic device #4, the control flow mapping table 302 mapsthe identifier value of 2001 to a pseudonym identifier value of 5002associated with the fourth wireless termination node.

Although the control flow mapping table 302 contemplates a one-to-onemapping between a particular electronic device and particular wirelesstermination node, one of ordinary skill in the art will appreciate thatvarious mapping schemes can be implemented. For example, in variousimplementations, an electronic device, as a result of a mobility event,moves within the coverage area of multiple WLANs. For example,electronic device #1 experiences a mobility event (e.g., mobile phoneuser walks near a coffee shop's Wi-Fi), causing the electronic device #1to move within the coverage area of the second wireless termination nodewhile remaining in the coverage area of the first wireless terminationnode. Consequently, the control flow mapping table 302 changes thepseudonym value from 3001 to [3001, 3005], wherein 3001 maps to thefirst wireless termination node and 3005 maps to the second wirelesstermination node.

As an exemplary operation of the control flow mapping table 302, BS #1,after associating with electronic device #1, sends a request includingan identifier value of 1001 to the networking device in order togenerate a control link with the networking device. Continuing with thisexample, the networking device generates a pseudonym value of 3001 forthe first wireless termination node. Continuing with this example, thenetworking device populates the control flow mapping table 302 with the1001 and 3001 identifier values in order to associate BS #1 with thefirst wireless termination node. In various implementations, one ofordinary skill in the art will appreciate that that the identifiersidentifying the base stations and the wireless termination can have avariety of values and/or formats.

The data flow mapping table 305 includes data tunnel identifiers inorder to map data tunnels identifiers between the two base stations andthe networking device, and in order to map data tunnel identifiersbetween the networking device and the four wireless termination nodes.With respect to the first electronic device, the data flow mapping table305 includes a data tunnel identifier value of 100 for identifying adata tunnel between the networking device and BS #1. With respect to thesecond electronic device, the data flow mapping table 305 includes adata tunnel identifier value of 101 for identifying a data tunnelbetween the networking device and BS #1. With respect to the thirdelectronic device, the data flow mapping table 305 includes a datatunnel identifier value of 200 for identifying a data tunnel between thenetworking device and BS #2. With respect to the fourth electronicdevice, the data flow mapping table 305 includes a data tunnelidentifier value of 201 for identifying a data tunnel between thenetworking device and BS #2.

The data flow mapping table 305 provides a mapping between the two basestations data tunnel identifiers and data tunnel identifiers associatedwith the four wireless termination nodes. The data flow mapping table305 provides data tunnel identifiers for the four wireless terminationnodes based on the base station data tunnel identifiers. With respect toelectronic device #1, the data flow mapping table 305 maps the datatunnel identifier value of 100 to a value of 300 associated with thedata tunnel of the first wireless termination node. With respect toelectronic device #2, the data flow mapping table 305 maps the datatunnel identifier value of 101 to a value of 301 associated with thedata tunnel of the second wireless termination node. With respect toelectronic device #3, the data flow mapping table 305 maps the datatunnel identifier value of 200 to a value of 500 associated with thedata tunnel of the third wireless termination node. With respect toelectronic device #4, the data flow mapping table 305 maps the datatunnel identifier value of 201 to a value of 501 associated with thedata tunnel of the fourth wireless termination node.

Although the data flow mapping table 305 contemplates a one-to-onemapping between a particular electronic device and particular wirelesstermination node, one of ordinary skill in the art will appreciate thatvarious mapping schemes can be implemented. For example, in variousimplementations, an electronic device, as a result of a mobility event,moves within the coverage area of multiple WLANs. For example,electronic device #2 experiences a mobility event (e.g., tablet userenter his building of employment), causing the electronic device #2 tomove within the coverage area of the third wireless termination nodewhile remaining in the coverage area of the second wireless terminationnode. Consequently, the data flow mapping table 305 changes the datatunnel identifier value from 301 to [301, 600], wherein 301 maps to thesecond wireless termination node data tunnel and 600 (not shown) maps tothe third wireless termination node data tunnel.

In some implementations, as shown in FIG. 4, the data flow mapping table305 includes a mapping between identification information associatedwith base station data tunnels and identification information associatedwith wireless termination node data tunnels. Data tunnels between thebase stations and the networking device are associated with a firstprotocol, and data tunnels between the wireless termination nodes andthe networking device are associated with a second protocol. As shown inFIG. 4, the data flow mapping table 305 includes a column for each ofthe base stations. In various implementations, one of ordinary skill inthe art will appreciate that the data flow mapping table 305 may bestructured and/or formatted differently.

In various implementations, a data packet received according to GTP-Uincludes a tunnel endpoint ID (TEID). In various implementations, a datapacket received according to GRE includes a GRE key. In someimplementations, the data flow mapper, based on information in the dataflow mapping table 305, replaces the TEID of a data packet received froma base station with a GRE key associated with the destination wirelesstermination node. In some implementations, the data flow mapper, basedon information in the data flow mapping table 305, replaces the GRE keyof a data packet received from a wireless termination node with a TEIDassociated with the destination base station.

As an exemplary operation of the data flow mapping table 305, thenetworking device receives a data packet from the second wirelesstermination node that is destined for electronic device #2. Continuingwith this example, the networking device changes the data packetidentifier value from 301 (e.g., a GRE key value) to 101 (e.g., a GTP-UTEID value). This way, the data packet is forwarded through the BS #2data tunnel in order to reach electronic device #2. As another exemplaryoperation of the data flow mapping table 305, the networking devicereceives a data packet originating at electronic device #4 that isdestined for the fourth wireless termination node. Continuing with thisexample, the networking device changes the data packet identifier valuesfrom 201 (e.g., a GTP-U TEID value) to 501 (e.g., a GRE key value). Thisway, the data packet is forwarded through the fourth wirelesstermination node data tunnel in order to reach the fourth wirelesstermination node.

FIG. 5 illustrates a conceptual diagram of a setup flow 500 associatedwith a networking device according to various implementations. FIG. 5includes a setup flow involving an electronic device 101, a base station104, a networking device 107, and a wireless termination node 106. It isto be appreciated that the setup flow is equally applicable to anetworking environment having more of any or all of these components.

According to some implementations, the networking device 107 sends asetup request 501 to the wireless termination node 106. The setuprequest 501 includes base station identification information.Accordingly, from the perspective of the wireless termination node 106,the networking device 107 appears to be a base station. In someimplementations, the setup request 501 corresponds to an Xw setuprequest message. In response, the wireless termination node 106 sends asetup response 502 to the networking device 107. In someimplementations, the setup response 502 corresponds to an Xw setupresponse message.

According to some implementations, the base station 104 sends a setuprequest 503 to the networking device 107. The setup request 503 includesidentification information of the base station 104. In someimplementations, the setup request 503 corresponds to an Xw setuprequest message. In response, the networking device 107 sends a setupresponse 504 to the base station 104. Accordingly, from the perspectiveof the base station 104, the networking device 107 appears to be awireless termination node. In some implementations, the setup response504 corresponds to an Xw setup response message. In variousimplementations, additional base stations (not shown) initiate setupprocedures with the networking device 107.

In some implementations, in response to the setup procedure between thebase station 104 and the networking device 107, the base station 104sends a reconfiguration request 505 to an electronic device 101 withwhich it is registered. In some implementations, the reconfigurationrequest 505 corresponds to an RRC_Connection_Reconfiguration message. Inresponse, the electronic device 101 sends a reconfiguration response 506to the base station 104. In some implementations, the reconfigurationresponse 506 corresponds to an RRC_Connection_Reconfiguration_Completemessage. In various implementations, after the electronic device 101sends the reconfiguration response 506, the electronic device 101 sendsa measurement report message (e.g., WLAN information) (not shown) to thebase station 104.

According to some implementations, the base station 104 sends anassociation request 507 to the networking device 107. The associationrequest 507 functions in part to request a wireless termination node toprepare resources for concurrent communications. For example, in someLWA implementations, the base station 104 (e.g., eNodeB) send theassociation request 507 to the wireless termination node 106 (e.g., WT)to prepare resources for LWA aggregation for the electronic device 101.In various implementations, the association request 507 includes anidentifier associated with the electronic device 101 and/or anidentifier identifying the data tunnel with which the base station 104is associated. In some implementations, the association request 507corresponds to an Xw addition request message. For example, in someimplementations, the association request 507 includes values indicativeof an eNBUeXwID, UEID, and/or eRABIDs (e.g., eNodeB TEIDs and PLMN ID).For example, the eNBUeXwID corresponds to an identifier associating theelectronic device 101 with the base station 104. For example, the UEIDcorresponds to an identifier identifying the electronic device 101. Forexample, the eRABIDs corresponds to identifiers identifying radio accessbearers (RABs), such as an evolved universal mobile telecommunicationssystem (UMTS) terrestrial radio access network (E-UTRAN) RAB.

In some implementations, in response to receiving the associationrequest 507, the networking device 107 sends a corresponding associationrequest 508 to the wireless termination node 106. The associationrequest 508 includes a mapped version of the identification informationcorresponding to the association request 507. In some implementations,the association request 508 corresponds to an Xw wireless terminationnode addition request message, such as an Xw WT addition requestmessage.

In some implementations, in response to receiving the associationrequest 508, the wireless termination node 106 sends the networkingdevice 107 an association response 509. In some implementations, theassociation response 509 corresponds to an Xw addition requestacknowledge message. For example, in some implementations, theassociation response 509 includes values indicative of a mappedeNBUeXwID, UEID, eRABIDs (e.g., XGW TEID), and/or WTUeXWid. For example,the WTUeXWid corresponds to an identifier associating the electronicdevice 101 with the wireless termination node 106.

In some implementations, in response to receiving the associationresponse 509, the networking device 107 sends a correspondingassociation response 510 to the base station 104. The associationresponse 510 includes identification information corresponding to theidentification information associated with the association request 507.In some implementations, the association response 510 corresponds to anXw addition request acknowledge message. For example, in someimplementations, the association response 510 includes values indicativeof eNBUeXwID, UEID, eRABIDs (e.g., XGW TEID), and/or WTUeXWid. At thispoint, a control link between the networking device 107 and wirelesstermination node 106 and a control link between the networking device107 and the base station 104 have been established.

According to some implementations, the base station 104 sends areconfiguration request 511 to the electronic device 101, which respondswith a reconfiguration response 512. At this point, the electronicdevice 101 is registered with the base station 104 and the wirelesstermination node 106.

According to some implementations, at 513 a, the networking device 107instantiates a data tunnel with the base station 104. In variousimplementations, the networking device 107 instantiates a GTP tunnelwith the base station 104 based on values corresponding to the eNodeBTEID and/or the XGW TEID.

According to some implementations, at 513 b, the networking device 107instantiates a data tunnel with the wireless termination node 106. Invarious implementations, the networking device 107 instantiates a GREtunnel with the wireless termination node 106 based on valuescorresponding to the XGW GRE key and/or the WT GRE key.

FIG. 6 illustrates a flowchart representation of a method 600 of linkgenerating and tunnel instantiating according to variousimplementations. According to various implementations, the method 600 isperformed by a networking device (e.g., networking device 107).According to various implementations, the method 600 is performed by anetworking device (e.g., the networking device 107 in FIGS. 1-3) withone or more processors and a non-transitory memory, wherein thenetworking device is communicatively coupled to a base station and oneor more wireless local area network (WLAN) termination nodes.

As represented by block 610, the method 600 includes detecting atrigger. According to various implementations, the networking device 107detects a trigger when a device establishes or attempts to establishconnectivity with the networking device 107. As one example, thenetworking device 107 detects the trigger when the electronic device 101establishes connectivity with the access point 105 and/or the basestation 104. As another example, the networking device 107 detects atrigger when the wireless termination node 106 establishes connectivitywith the networking device 107. As yet another example, the networkingdevice 107 detects a trigger when the base station 104 establishesconnectivity with the networking device 107. According to variousimplementations, the networking device 107 detects a trigger when thenetworking device 107 receives a request to associate the base station104 with the wireless termination node 106. According to variousimplementations, the networking device 107 detects a trigger when thenetworking device 107 receives a registration request associated withthe electronic device 101 from the base station 104.

As represented by block 620, the method 600 includes generating controllinks and populating a control flow mapping table. According to variousimplementations, the networking device 107 or a component thereof (e.g.,the link generator 301 in FIG. 3) generates a control link between thenetworking device 107 and the base station 104 based on a firstidentifier associated with the base station 104. According to variousimplementations, the networking device 107 or a component thereof (e.g.,the link generator 301 in FIG. 3) generates control links between thenetworking device 107 and a plurality of wireless termination nodes(e.g., including the first wireless termination node described withreference to blocks 630-640 and the new wireless termination nodedescribed with reference to blocks 660-670) based on a second identifierassociated with the base station 104. As such, there is an M×N number ofcontrol links (e.g., Xw links), where M is the number of base stationsand N is the number of wireless termination nodes. This is fewer thanthe M×N number of control links present in current systems, resulting inresource savings.

In various implementations, the second identifier corresponds to apseudonym for the base station 104. By using a pseudonym for the basestation 104, the networking device 107 appears to be a base station fromthe perspective of the wireless termination node 106, and appears to bea wireless termination node from the perspective of the base station104. Accordingly, mobility events of the electronic device 101 occurseamlessly and are hidden from the base station 104. For example, amobility event can cause a hand-off of service between wirelesstermination nodes. This service hand-off is transparent from theperspective of the base station 104 due to the abstraction or decouplingperformed by the networking device 107.

According to various implementations, the networking device 107 or acomponent thereof (e.g., the control flow mapper 303 in FIG. 3)associates or otherwise links the first and second identifiers bycreating a new entry within the control flow mapping table (e.g., thecontrol flow mapping table 302 in FIGS. 3 and 4). For example, withreference to the first column of the control mapping table 302 of FIG.4, the networking device 107 populates the control flow mapping table302 with an identifier having a value of 1001 for BS #1 and generates alink with BS #1 according to the identifier. Continuing with theexample, the networking device 107, based on the identifier, generates apseudonym identifier having a value of 3001 for the first wirelesstermination node. Continuing with the example, the networking device 107generates a link with the first wireless termination node according tothe pseudonym identifier.

As represented by block 630, the method 600 includes instantiating afirst set of data tunnels and populating a data flow mapping table.According to various implementations, the networking device 107 or acomponent thereof (e.g., the tunnel instantiator 304 in FIG. 3)instantiates the first set of data tunnels. In some implementations, thefirst set of data tunnels includes: (A) a first data tunnel between thebase station and the networking device 107 according to a firsttunneling protocol (e.g., GTP); and (B) a second data tunnel between thenetworking device 107 and a first wireless termination node according toa second tunneling protocol (e.g., GRE). According to variousimplementations, the first set of data tunnels are instantiated inresponse to the trigger detected in block 610, such as when theelectronic device 101 moves within the coverage area of the firstwireless termination node.

According to various implementations, the networking device 107 or acomponent thereof (e.g., the data flow mapper 306 in FIG. 3) associatesor otherwise links the first and second data tunnels by creating a newentry within the data flow mapping table (e.g., the data flow mappingtable 305 in FIGS. 3 and 4). The association informs data packetforwarding decisions, and allows the base station and the first wirelesstermination node to receive data packets according to theirnative/preferred tunneling protocol. For example, in someimplementations, the base station 104 can receive and transmit datapackets across the first data tunnel according to the GTP-U protocol. Asanother example, in some implementations, the wireless termination node106 can receive and transmit data packets across the second data tunnelaccording to the GRE protocol.

In some implementations, the data flow mapping table 305 includes amapping between an identifier associated with the first data tunnel andan identifier associated with the second data tunnel. For example, withreference to the data mapping table 305 of FIG. 4, the row entry valuesof 200 and 500 indicate a mapping between a data tunnel identifierassociated with BS #2 and a data tunnel identifier associated with thethird wireless termination node.

As represented by block 640, the method 600 includes forwarding datapackets between the base station 104 and the first wireless terminationnode via the first set of data tunnels based on the data flow mappingtable. For example, with reference to the data flow mapping table 305 inFIG. 4, the networking device 107 receives a data packet from the secondwireless termination node according to GRE. Continuing with thisexample, the networking device 107 changes the identifier of the datapacket from a value of 301 to 101 (e.g., a GTP-U TEID value). Continuingwith this example, the networking device 107 forwards the modified datapacket towards BS #1 through the data tunnel identified by the value of101.

As represented by block 650, the method 600 includes detecting amobility event associated with the electronic device 101. In variousimplementations, the mobility event occurs when the electronic device101 moves (or roams) from the coverage area serviced by the firstwireless termination node to a new coverage area services by a newwireless termination node. For example, with reference to FIG. 2, themobility event occurs when the electronic device 101 moves from thecoverage area of wireless termination node 106 a to the coverage area ofwireless termination node 106 b. Continuing with this example, in someimplementations, the electronic device 101 remains within the coveragearea of wireless termination node 106 a after moving to the coveragearea of wireless termination node 106 b.

As represented by block 660, the method 600 includes instantiating asecond set of data tunnels and updating the data flow mapping table.According to various implementations, the networking device 107 or acomponent thereof (e.g., the tunnel instantiator 304 in FIG. 3)instantiates the second set of data tunnels. In some implementations,the second set of data tunnels includes: (A) the first data tunnelbetween the base station and the networking device 107 according to thefirst tunneling protocol (e.g., GTP); and (B) a third data tunnelbetween the networking device 107 and the new wireless termination nodeaccording to the second tunneling protocol (e.g., GRE). According tovarious implementations, the second set of data tunnels are instantiatedin response to the mobility event detected in block 650 (e.g., theelectronic device 101 moves from the coverage area serviced by the firstwireless termination node to the coverage area serviced by the newwireless termination node). According to various implementations, thenetworking device 107 or a component thereof (e.g., the data flow mapper306 in FIG. 3) updates the data flow mapping table (e.g., the data flowmapping table 305 in FIGS. 3 and 4) to include an association or linkbetween the first and third data tunnels.

As represented by block 670, the method 600 includes forwarding datapackets between the base station and the new wireless termination nodevia the second set of data tunnels based on the data flow mapping table.For example, with reference to the data flow mapping table 305 in FIG.4, the mapping table 305 includes a 100:300 mapping between BS #1 andthe first wireless termination node before the networking device detectsa mobility event of electronic device #1. Continuing with this example,the networking device detects the mobility event (e.g., at block 650),wherein electronic device #1 moves from the coverage area of the firstwireless termination node to the coverage areas of both the first andsecond wireless termination nodes. Continuing with this example, inresponse to detecting the mobility event, the networking device updatesthe data flow mapping table from 100:300 to 100: [300, 301], wherein 300and 301 corresponds to the first and second wireless termination nodes,respectively. Continuing with this example, based on the updatedmapping, the networking device forwards a received data packet having anidentifier value of 300 and/or 301 towards electronic device #1, andforwards a received data packet having an identifier value of 100 to thefirst wireless termination node and/or the second wireless terminationnode.

FIGS. 7A-7C illustrate a flowchart representation of a method 700 oflink generating and tunnel instantiating according to variousimplementations. According to various implementations, the method 700 isperformed by a networking device (e.g., networking device 107).According to various implementations, the method 700 is performed by anetworking device (e.g., the networking device 107 in FIGS. 1-3) withone or more processors and a non-transitory memory, wherein thenetworking device is communicatively coupled to a base station and oneor more wireless local area network (WLAN) termination nodes.

With reference to FIG. 7A, as represented by block 710, the method 700includes obtaining, at the networking device, a request to associate oneor more electronic devices with the one or more WLAN termination nodes,wherein the one or more electronic devices are associated with the basestation. In various implementations, as represented by block 710 a, thenetworking device is collocated with a security gateway (SecGW) node ina LTE-WLAN radio level integration with IPsec tunnel (LWIP) deployment.In various implementations, as represented by block 710 b, thenetworking device is collocated with an X2 gateway node. In variousimplementations, as represented by block 710 c, the base stationcorresponds to an eNodeB in a LTE-WLAN aggregation (LWA) deployment.

As represented by block 720, the method 700 includes in response toobtaining the request to associate the one or more electronic deviceswith the one or more WLAN termination nodes: generating, between thebase station and the networking device, a control link based at least inpart on a first identifier included in the request, wherein the firstidentifier is associated with the base station; generating, between thenetworking device and the first WLAN termination node among the one ormore WLAN termination nodes, a control link based at least in part on asecond identifier associated with the base station, wherein the secondidentifier corresponds to a pseudonym for the base station; andassociating the first identifier with the second identifier in a controlflow mapping table. As represented by block 730, the method 700 includesinstantiating, between the base station and the networking device, afirst data tunnel associated with a first tunneling protocol.

With reference to FIG. 7B, the flowchart continues to block 740, whereinthe method 700 includes instantiating, between the networking device andthe first WLAN termination node among the one or more WLAN terminationnodes, a second data tunnel associated with a second tunneling protocoldifferent from the first tunneling protocol.

As represented by block 750, the method includes associating the firstdata tunnel with the second data tunnel in a data flow mapping table. Invarious implementations, as represented by block 750 a, the data flowmapping table includes entries mappings between GPRS tunneling protocoluser plane (GTP-U) tunnel endpoint identifiers (TEID) associated withthe first data tunnel and generic routing encapsulation (GRE) keysassociated with the second data tunnel.

As represented by block 760, in various implementations, the method 700includes forwarding one or more data packets received from the basestation via the first data tunnel to the first WLAN termination node viathe second data tunnel based on the association between the first andsecond data tunnels in the data flow mapping table. As represented byblock 770, in various implementations, the method 700 includesforwarding one or more data packets received from the first WLANtermination node via the second data tunnel to the base station via thefirst data tunnel based on the association between the first and seconddata tunnels in the data flow mapping table.

With reference to FIG. 7C, the flowchart continues to block 780, whereinthe method 700 includes, in various implementations, in response toobtaining the request to associate the one or more electronic deviceswith the one or more WLAN termination nodes, generating, between thenetworking device and a second WLAN termination node among the one ormore WLAN termination nodes, a control link based at least in part onthe second identifier associated with the base station, wherein thesecond identifier corresponds to the pseudonym for the base station. Asrepresented by block 780 a, in various implementations, the method 700includes in response to a mobility event that transitions service of atleast a subset of the one or more electronic devices from the first WLANtermination node to the second WLAN termination node: instantiating,between the networking device and a second WLAN termination node amongthe one or more WLAN termination nodes, a third data tunnel associatedwith the second tunneling protocol; and associating the first datatunnel with the third data tunnel in the data flow mapping table. Themobility event is transparent to the base station as the second WLANtermination interacts with the at least a subset of the one or moreelectronic devices.

As represented by block 780 b, in various implementations, the method700 includes forwarding one or more data packets received from the basestation via the first data tunnel to the second WLAN termination nodevia the third data tunnel based on the association between the first andthird data tunnels in the data flow mapping table. As represented byblock 780 c, in various implementations, the method 700 includesforwarding one or more data packets received from the second WLANtermination node via the third data tunnel to the base station via thefirst data tunnel based on the association between the first and thirddata tunnels in the data flow mapping table.

FIG. 8 illustrates a block diagram of an example of a networking device800 in accordance with various implementations. For example, in someimplementations, the networking device 800 is similar to and adaptedfrom the networking device 108 of FIG. 1. While certain specificfeatures are illustrated, those skilled in the art will appreciate fromthe present disclosure that various other features have not beenillustrated for the sake of brevity, and so as not to obscure morepertinent aspects of the implementations disclosed herein. To that end,as a non-limiting example, in some implementations the networking device800 includes one or more processing units (CPUs) 802, a memory 810, anetwork interface 803, a programming (I/O) interface 805, and one ormore communication buses 804 for interconnecting these and various othercomponents. In some implementations, the one or more communication buses804 include circuitry that interconnects and controls communicationsbetween system components.

The memory 810 includes high-speed random-access memory, such as DRAM,SRAM, DDR RAM, or other random access solid state memory devices. Insome implementations, the memory 810 includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid-state storagedevices. The memory 810 optionally includes one or more storage devicesremotely located from the one or more CPUs 802. The memory 810 comprisesa non-transitory computer readable storage medium. In someimplementations, the memory 810 or the non-transitory computer readablestorage medium of the memory 810 stores the following programs, modulesand data structures, or a subset thereof including an optional operatingsystem 820, a link generator 301, a control flow mapping table 302, acontrol flow mapper 303, a tunnel instantiator 304, a data flow mappingtable 305, and a data flow mapper 306.

The link generator 301 is configured to generate control links betweenbase stations and wireless termination nodes. To that end, in variousimplementations, the link generator 301 includes instructions and/orlogic 830 a, and heuristics and data 830 b. The mapping informationgenerated in conjunction with the control link generation is stored inthe control flow mapping table 302.

The control flow mapper 303 is configured to map control packets betweenthe base stations and the wireless termination nodes. To that end, invarious implementations, the control flow mapper 303 includesinstructions and/or logic 840 a, and heuristics and data 840 b. Thecontrol flow mapper 303 utilizes the control flow mapping table 302 inorder to facilitate control packet mapping.

The tunnel instantiator 304 is configured to instantiate data tunnelsbetween the networking device 800 and the base stations. The tunnelinstantiator 304 is further configured to instantiate data tunnelsbetween the networking device 800 and the wireless termination nodes. Tothat end, in various implementations, the tunnel instantiator 304includes instructions and/or logic 850 a, and heuristics and data 850 b.The mapping information generated in conjunction with the tunnelinstantiation is stored in the data flow mapping table 305.

The data flow mapper 306 is configured to map data packets between basestations and wireless termination nodes. To that end, in variousimplementations, the data flow mapper 306 includes instructions and/orlogic 860 a, and heuristics and data 860 b. The data flow mapper 306utilizes the data flow mapping table 305 in order to facilitate datapacket mapping.

Moreover, FIG. 8 is intended more as functional description of thevarious features which can be present in a particular embodiment asopposed to a structural schematic of the implementations describedherein. As recognized by those of ordinary skill in the art, items shownseparately could be combined and some items could be separated. Forexample, some functional modules shown separately in FIG. 8 could beimplemented in a single module and the various functions of singlefunctional blocks could be implemented by one or more functional blocksin various implementations. The actual number of modules and thedivision of particular functions and how features are allocated amongthem will vary from one embodiment to another and, in someimplementations, depends in part on the particular combination ofhardware, software, and/or firmware chosen for a particular embodiment.

While various aspects of implementations within the scope of theappended claims are described above, it is to be appreciated that thevarious features of implementations described above may be embodied in awide variety of forms and that any specific structure and/or functiondescribed above is merely illustrative. It is to be appreciated that anaspect described herein may be implemented independently of any otheraspects and that two or more of these aspects may be combined in variousways. For example, an apparatus may be implemented and/or a method maybe practiced using any number of the aspects set forth herein. Inaddition, such an apparatus may be implemented and/or such a method maybe practiced using other structure and/or functionality in addition toor other than one or more of the aspects set forth herein.

It will also be understood that, although the terms “first,” “second,”etc. may be used herein to describe various elements, these elements arenot limited by these terms. These terms are only used to distinguish oneelement from another. For example, a first outgoing label could betermed a second outgoing label, and, similarly, a second outgoing labelcould be termed a first outgoing label, which changing the meaning ofthe description, so long as all occurrences of the “first outgoinglabel” are renamed consistently and all occurrences of the secondoutgoing label are renamed consistently. The first outgoing label andthe second outgoing label are both outgoing labels, but they are not thesame outgoing label.

What is claimed is:
 1. A method comprising: at a networking device with one or more processors and a non-transitory memory, the networking device communicatively coupled to a base station and one or more wireless local area network (WLAN) termination nodes: obtaining a request to associate one or more electronic devices with the one or more WLAN termination nodes, wherein the one or more electronic devices are associated with the base station; in response to obtaining the request to associate the one or more electronic devices with the one or more WLAN termination nodes: generating, between the base station and the networking device, a control link based at least in part on a first identifier included in the request, wherein the first identifier is associated with the base station; generating, between the networking device and a first WLAN termination node among the one or more WLAN termination nodes, a control link based at least in part on a second identifier associated with the base station, wherein the second identifier corresponds to a pseudonym for the base station; and associating the first identifier with the second identifier in a control flow mapping table; instantiating, between the base station and the networking device, a first data tunnel associated with a first tunneling protocol; instantiating, between the networking device and the first WLAN termination node among the one or more WLAN termination nodes, a second data tunnel associated with a second tunneling protocol different from the first tunneling protocol; and associating the first data tunnel with the second data tunnel in a data flow mapping table.
 2. The method of claim 1, further comprising forwarding one or more data packets received from the base station via the first data tunnel to the first WLAN termination node via the second data tunnel based on the association between the first and second data tunnels in the data flow mapping table.
 3. The method of claim 1, further comprising forwarding one or more data packets received from the first WLAN termination node via the second data tunnel to the base station via the first data tunnel based on the association between the first and second data tunnels in the data flow mapping table.
 4. The method of claim 1, wherein the data flow mapping table includes entries mappings between GPRS tunneling protocol user plane (GTP-U) tunnel endpoint identifiers (TEID) associated with the first data tunnel and generic routing encapsulation (GRE) keys associated with the second data tunnel.
 5. The method of claim 1, wherein the base station corresponds to an eNodeB in a LTE-WLAN aggregation (LWA) deployment.
 6. The method of claim 1, wherein the networking device is collocated with a security gateway (SecGW) node in a LTE-WLAN radio level integration with IPsec tunnel (LWIP) deployment.
 7. The method of claim 1, wherein the networking device is collocated with an X2 gateway node.
 8. The method of claim 1, further comprising: in response to obtaining the request to associate the one or more electronic devices with the one or more WLAN termination nodes, generating, between the networking device and a second WLAN termination node among the one or more WLAN termination nodes, a control link based at least in part on the second identifier associated with the base station, wherein the second identifier corresponds to the pseudonym for the base station.
 9. The method of claim 8, further comprising: in response to a mobility event that transitions service of at least a subset of the one or more electronic devices from the first WLAN termination node to the second WLAN termination node: instantiating, between the networking device and a second WLAN termination node among the one or more WLAN termination nodes, a third data tunnel associated with the second tunneling protocol; and associating the first data tunnel with the third data tunnel in the data flow mapping table.
 10. The method of claim 9, further comprising forwarding one or more data packets received from the base station via the first data tunnel to the second WLAN termination node via the third data tunnel based on the association between the first and third data tunnels in the data flow mapping table.
 11. The method of claim 9, further comprising forwarding one or more data packets received from the second WLAN termination node via the third data tunnel to the base station via the first data tunnel based on the association between the first and third data tunnels in the data flow mapping table.
 12. A non-transitory memory storing one or more programs, which, when executed by one or more processors of a networking device communicatively coupled to a base station and one or more wireless local area network (WLAN) termination nodes, cause the networking device to: obtain a request to associate one or more electronic devices with the one or more WLAN termination nodes, wherein the one or more electronic devices are associated with the base station; in response to obtaining the request to associate the one or more electronic devices with the one or more WLAN termination nodes: generate, between the base station and the networking device, a control link based at least in part on a first identifier included in the request, wherein the first identifier is associated with the base station; generate, between the networking device and a first WLAN termination node among the one or more WLAN termination nodes, a control link based at least in part on a second identifier associated with the base station, wherein the second identifier corresponds to a pseudonym for the base station; and associate the first identifier with the second identifier in a control flow mapping table; instantiate, between the base station and the networking device, a first data tunnel associated with a first tunneling protocol; instantiate, between the networking device and the first WLAN termination node among the one or more WLAN termination nodes, a second data tunnel associated with a second tunneling protocol different from the first tunneling protocol; and associate the first data tunnel with the second data tunnel in a data flow mapping table.
 13. The non-transitory memory of claim 12, wherein the one or more programs further cause the networking device to: forward one or more data packets received from the base station via the first data tunnel to the first WLAN termination node via the second data tunnel based on the association between the first and second data tunnels in the data flow mapping table.
 14. The non-transitory memory of claim 12, wherein the data flow mapping table includes entries mappings between GPRS tunneling protocol user plane (GTP-U) tunnel endpoint identifiers (TEID) associated with the first data tunnel and generic routing encapsulation (GRE) keys associated with the second data tunnel.
 15. The non-transitory memory of claim 12, wherein the one or more programs further cause the networking device to: in response to obtaining the request to associate the one or more electronic devices with the one or more WLAN termination nodes, generate, between the networking device and a second WLAN termination node among the one or more WLAN termination nodes, a control link based at least in part on the second identifier associated with the base station, wherein the second identifier corresponds to the pseudonym for the base station.
 16. The non-transitory memory of claim 15, wherein the one or more programs further cause the networking device to: in response to a mobility event that transitions service of at least a subset of the one or more electronic devices from the first WLAN termination node to the second WLAN termination node: instantiate, between the networking device and a second WLAN termination node among the one or more WLAN termination nodes, a third data tunnel associated with the second tunneling protocol; and associate the first data tunnel with the third data tunnel in the data flow mapping table.
 17. A networking device, comprising: one or more processors; a non-transitory memory; and one or more programs stored in the non-transitory memory, which, when executed by the one or more processors, cause the networking device to: obtain a request to associate one or more electronic devices with one or more wireless local area network (WLAN) termination nodes, wherein the one or more electronic devices are associated with a base station; in response to obtaining the request to associate the one or more electronic devices with the one or more WLAN termination nodes: generate, between the base station and the networking device, a control link based at least in part on a first identifier included in the request, wherein the first identifier is associated with the base station; generate, between the networking device and a first WLAN termination node among the one or more WLAN termination nodes, a control link based at least in part on a second identifier associated with the base station, wherein the second identifier corresponds to a pseudonym for the base station; and associate the first identifier with the second identifier in a control flow mapping table; instantiate, between the base station and the networking device, a first data tunnel associated with a first tunneling protocol; instantiate, between the networking device and the first WLAN termination node among the one or more WLAN termination nodes, a second data tunnel associated with a second tunneling protocol different from the first tunneling protocol; and associate the first data tunnel with the second data tunnel in a data flow mapping table.
 18. The networking device of claim 17, wherein the data flow mapping table includes entries mappings between GPRS tunneling protocol user plane (GTP-U) tunnel endpoint identifiers (TEID) associated with the first data tunnel and generic routing encapsulation (GRE) keys associated with the second data tunnel.
 19. The networking device of claim 17, wherein the one or more programs further cause the networking device to: in response to obtaining the request to associate the one or more electronic devices with the one or more WLAN termination nodes, generate, between the networking device and a second WLAN termination node among the one or more WLAN termination nodes, a control link based at least in part on the second identifier associated with the base station, wherein the second identifier corresponds to the pseudonym for the base station.
 20. The networking device of claim 19, wherein the one or more programs further cause the networking device to: in response to a mobility event that transitions service of at least a subset of the one or more electronic devices from the first WLAN termination node to the second WLAN termination node: instantiate, between the networking device and a second WLAN termination node among the one or more WLAN termination nodes, a third data tunnel associated with the second tunneling protocol; and associate the first data tunnel with the third data tunnel in the data flow mapping table. 